Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1363

reference: 202-tree-1
name: 1363
tree-preservation-order: undefined
202-tpo-1
uprn
address-text
point: POINT (-1.026589 50.864868)
geometry: MULTIPOLYGON (((-1.026560 50.864864,-1.026562 50.864870,-1.026566 50.864875,-1.026580 50.864882,-1.026588 50.864883,-1.026597 50.864882,-1.026612 50.864875,-1.026616 50.864871,-1.026617 50.864865,-1.026616 50.864859,-1.026612 50.864854,-1.026606 50.864850,-1.026589 50.864847,-1.026572 50.864850,-1.026566 50.864854,-1.026560 50.864864)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL